Click any tag below to further narrow down your results
+ agentic engineering
(1)
+ careers
(1)
+ junior developer training
(1)
+ software engineering
(1)
+ automation
(1)
+ development tools
(1)
+ git worktrees
(1)
+ orca
(1)
+ productivity
(1)
+ lennys podcast
(1)
+ reasoning models
(1)
+ agent security
(1)
+ llm code generation
(1)
+ collaboration
(1)
+ iteration
(1)
Links
Jake Goldsborough argues that AI coding agents aren't killing software engineering—they're freeing engineers from tedious mechanical work so they can focus on the actual problem-solving that defines the craft. The hard parts that never mattered (regex wrestling, syntax memorization, build system incantations) are disappearing, but the work that requires real judgment and responsibility remains.
- The difficult parts of coding—parsing edge cases, remembering obscure syntax, navigating unfamiliar codebases—were never the point; they were tolls between understanding a problem and solving it, and removing them doesn't diminish engineering skill.
- Agents handle syntax and scaffolding faster, which lets engineers explore domains that were previously too expensive (rewriting programs in different languages, understanding unfamiliar systems, testing experimental ideas), actually tightening the learning loop rather than replacing it.
- The real shift is architectural: engineering moves from "produce every character by hand" to "direction, judgment, verification, and responsibility," and the actual risk isn't that the work disappears but that companies cut people, generated code creates failures at scale, and the junior-to-senior training path collapses.
Orca lets you run multiple code-generation agents (Codex, ClaudeCode, Pi, etc.) side-by-side in isolated git worktrees and compare or merge their outputs. It combines split terminals, UI scraping, remote execution, commit workflows, and real-time mobile notifications to manage and steer agents without context switching.
- Orca runs multiple AI coding agents (Codex, ClaudeCode, OpenCode, Pi, etc.) in parallel using isolated git worktrees, so you can fan out one prompt to several agents and merge the best output.
- It bundles a full dev environment—WebGL terminal, embedded VS Code with autosave, and Chromium-based UI scraping to capture HTML/CSS/screenshots directly into prompts.
- Mobile apps (iOS/Android) let you get notified when agents finish or need input, then steer them, review PRs, and comment on diffs remotely.
- It's MIT-licensed and open source, installable via Homebrew, AUR, or prebuilt binaries, with every action scriptable via CLI commands.
The article summarizes highlights from a podcast episode discussing recent advancements in AI and their impact on software engineering, particularly the emergence of coding agents. It covers topics like the inflection point in model capabilities, the changing role of software engineers, and the challenges faced by mid-career professionals.
- GPT 5.1 and Claude Opus 4.5 (released in November) marked a real inflection point where generated code became reliably functional rather than needing constant oversight
- The bottleneck in software development has shifted from writing code to testing it, since prototyping is now fast and cheap
- Running multiple coding agents simultaneously is mentally exhausting and risks burnout if overused
- Interruptions are now less costly to productivity since these tools let programmers pick back up quickly after breaks
In a podcast discussion, predictions for the tech industry in 2026 are shared, highlighting the undeniable improvement of LLMs in writing code, advancements in coding agent security, and the potential obsolescence of manual coding. Other predictions include a successful breeding season for Kākāpō parrots and the implications of AI-assisted programming on software engineering careers.
- LLMs will keep getting undeniably better at writing code through 2026, shifting more programming work to coding agents
- Security around coding agents will become a major focus as they gain more autonomy and access to systems
- Manual hand-coding may start becoming obsolete for significant portions of software engineering work, reshaping the profession
- Kākāpō parrots are predicted to have a successful breeding season in 2026
Exploring the effectiveness of coding agents hinges on effective user input, constraints, and context. By applying Steven Johnson's patterns for generating ideas, the article demonstrates how to enhance coding agent outputs through structured prompting and feedback mechanisms. This approach encourages incremental development, reuses existing solutions, and fosters a collaborative environment between humans and AI.
- Coding agents produce better output when users apply Steven Johnson's "good ideas" patterns (adjacent possible, liquid networks, slow hunches) as prompting strategies rather than treating the agent as a one-shot answer machine.
- Structured constraints and iterative feedback loops—not just clearer instructions—are what actually improve agent performance, mirroring how innovation historically emerges from recombination rather than isolated genius.
- Treating coding agents as collaborators to think alongside, rather than tools to extract finished answers from, leads to more incremental, reusable, and higher-quality code.
The article reviews significant trends and developments in the LLM space throughout 2025, highlighting breakthroughs in reasoning, the rise of coding agents, and the increasing use of LLMs in command-line interfaces. It notes the evolution of tools and models, including the impact of asynchronous coding agents and the normalization of YOLO mode for improved efficiency.
- Reasoning models became mainstream in 2025, significantly boosting LLM performance on complex tasks
- Coding agents surged in popularity, with asynchronous agents enabling developers to offload larger chunks of work
- "YOLO mode" (letting agents run commands without manual approval) went from risky novelty to normalized practice for efficiency
- LLMs increasingly moved into command-line interfaces, embedding AI more directly into developer workflows